home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Experimental BBS Explossion 3
/
Experimental BBS Explossion III.iso
/
gus
/
digestv5.zip
/
V5N25M.TXT
< prev
next >
Wrap
Text File
|
1994-02-28
|
8KB
|
176 lines
Apparently-To: john.smith@gravis.com
GUS Musician's Digest Sun, 27 Feb 94 3:53 erv Volume 5: Issue 25
Today's Topics:
Custom Patches
MUSIC NEWBIE NEEDS HELP!
The Patch List
Standard Info:
- Meta-info about the GUS can be found at the end of the Digest.
- Before you ask a question, please READ THE FAQ.
----------------------------------------------------------------------
Date: Sat, 26 Feb 1994 14:26:38 -0800
From: dna@netcom.com (David Altekruse)
Subject: Custom Patches
Perhaps an important category in organizing custom patches is whether
it is intended for use as a GM patch as a possible substitute for the
current ones from Gravis/Eye&I, or as a non-GM patch because it isn't
a GM instrument or because of its size (like the bosen_l patches).
The primary reason I am posting this, though, is to see if anyone has
suggestions concerning the handling of patch revisions and of multiple
versions of the same instrument. This is of particular interest to me
since I am about to submit a couple harpsichord patches as well as yet
another revision of the bosen_l.pat and a smaller piano patch.
For example, when I came up with the first Bosendorfer piano patch I
named it bosen_l.pat (l for large) in order to allow for a bosen_s.pat
(for small) which I still haven't submitted. Then when I came up with
a new revision of bosen_l.pat which I intended to be a replacement for
it, I called it bosen_l2.pat (I wished I would have had the foresight
to have named the first one bosen_l1.pat). I thought a change in file
name was a good idea so people would realize that it wasn't the same
file they already had. However, now what's happened is that some people
think they are two different sounds, not just 'upgrades' and I haven't
been able to get anyone to remove the old bosen_l.pat on the mirror
sites. Now I'm wondering if I shouldn't have just kept the original
name (bosen_l.pat) throughout revisions.
So does anyone have any suggestions on the best way to handle multiple
versions (bosen_l.pat and bosen_s.pat situation) or to handle revisions
(bosen_l2.pat and, say, bosen_l3.pat)? Or is this a "don't care"?
- David Altekruse, dna@netcom.com
------------------------------
Date: Sun, 27 Feb 1994 02:13:07 +0800 (WST)
From: Roderick Nasir DAVID <ruffus@tartarus.uwa.edu.au>
Subject: MUSIC NEWBIE NEEDS HELP!
G'day guys,
Right. Heres the problem. I mainly use my GUS for games *grin* but
now I wanna take advantage of the music capablitites of the GUS.
I've got a 1Meg GUS, with the midi box and a midi keyboard plus
the Midisoft recording sessions sequencer (2.06 disks) . So in
a nutshell....
WHERE DO I GO FROM HERE??!! (lets put it this way, is iMIDI IN to
MIDI OUT or????? )
I'm sorry if this is a really silly ask. I've looked EVERYWHERE for FAQ's
on this, but to no avail, nothing..
Thanx HEAPS in advance,
-----
Nasir
--
* Seeya on the Groove Train! | "When you get somewhere......You're there" *
* _+-_|\ | Buckaroo Banzai. *
* / \ | Nasir David at the... *
* Perth , W.A ----> +_.--._/ | University Of Western Australia. *
------------------------------
Date: Sun, 27 Feb 1994 13:40:34 +0800 (WST)
From: tclee@iss.nus.sg (Lee Teck Chee)
Subject: The Patch List
> From: chrisw@popserver.stanford.edu (Chris Wilkins)
>
> You are doing a great public service! The question is, how will this
> list be updated? Are you volunteering to have all people submitting
> new patches mail a description to you? (Fine by me).
As long as I am aware that new patches have appeared, I will check them
out. If there is a doc file describing the patch, that's best for me. It
would also be easier for me if everyone who submits new patches mail
some description to me. I have also written a simple program that would
extract all the necessary information (for the list) out of the patch
format header so as long as the anyone finds a patch, they can mail me
this information to be updated in the list.
> You've left out a really important one in the properties though: size!
> Particularly for modem downloaders and those with < 1M Gusses. Also,
> you should probably have looped / unlooped as well as a property.
Agreed. I will add them in.
> Also, it would be useful to have cross references for patches which
> have something in common. eg. patches which are smaller versions of
Yes, this would be good. However, this requires that patch authors
document their patch files properly and completely. The current patches
I can find on epas (about 9MB worth) are not that well documented in
this area. If we can have a standard form to be filled in, and included
with every new patch (much like Linux's LSM entries), the custom patch
scene would be more organized.
> The tricky thing is going to be defining synthy patches I guess, put
> the usual sort of bass / lead / pad / FX sort of classification would
> probably be O.K.
Alright. I'll just use the present organization for the time being, once
the list is out, feel free to suggest new sub-divisions.
> From: hst@mh.nl (Klaas Hemstra)
>
> In the previous digest Lee Teck Chee (tclee@iss.nus.sg) sought for
> views on how to organize custom patches.
>
> First i would like to say that i think the discussion should really be
> about how we can use all these custom patches in a user-friendly
> manner. More to the point: How can we program the GUS windows driver
> to use the patches from a Standard MIDI file, together with normal
I believe Phat has mentioned that Gravis/Forte are working on the best
way to handle the patch banking business. Once this is finalized, I will
include the information in the list. Also, note that what I am doing is
a custom patch user guide and not a patchmaker guide (there is already
an excellent one out there).
> My opinion is that you should place patches that simulate the same
> instrument in another bank, with the same patch number. That is the
That is why I am categorizing them based on GM standard, and I have a
column for suggested/possible replacement.
WildCat
------------------------------
End of GUS Musician's Digest V5 #25
***********************************
To post to tomorrow's digest: <gus-music@mail.orst.edu>
To (un)subscribe or get help: <gus-music-request@mail.orst.edu>
To contact a human (last resort): <gus-music-owner@mail.orst.edu>
FTP Sites Archive Directories
--------- ------- -----------
Main N.American Site: archive.orst.edu pub/packages/gravis
wuarchive.wustl.edu systems/ibmpc/ultrasound
Main Asian Site: nctuccca.edu.tw PC/ultrasound
European Callers ONLY: theoris.rz.uni-konstanz.de pub/sound/gus
Submissions: archive.epas.utoronto.ca pub/pc/ultrasound/submit
Newly Validated Files: archive.epas.utoronto.ca pub/pc/ultrasound
Mirrors: garbo.uwasa.fi mirror/ultrasound
MailServer For Archive Access: Email to <mail-server@nike.rz.uni-konstanz.de>
Hints:
- Get the FAQ from the FTP sites or the request server.
- Mail to <gus-music-request@mail.orst.edu> for info about other
GUS related mailing lists (general use, programmers, etc.).